-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rpi-kernel: update to 6.1.54 (and rpi-firmware, rpi-userland, rpi-eeprom) #46152
Conversation
|
As far as I gather |
I'm aware, Leah was looking into the others |
I think I might have a potential solution for this. With a lot of tracing, I was able to make
The infinite loop was fixed by adding An accordingly modified After building and installing the packages, dkms works fine:
I'm not sure if my approach is correct. I also checked how other's distribution packages are handling that. In the Raspberry Pi OS Debian package, the binaries are already included. Instead of adding multiple different files scattered across the kernel sources, that would be maybe the better approach. However, I didn't find out yet how you can also cross-compile them to deliver them in the package. |
yes, rpios builds it natively so that works. it's not supported to build those tools for the target so to do so would require patching will try adding those files later (after the weekend) |
Indeed, it's not supported to build them for the target. I found this old post in the kernel archives from 2013, where someone wanted to enable this. However, it got rejected. 😞 |
fe5db64
to
cc12437
Compare
I was able to get it to work with fewer files added (see cc12437), why did you need to add the vdso stuff? also, will post builds for all to test tomorrow |
It just didn't work for me without them. If
Subsequently, |
I was testing on aarch64-musl (rpi4), also was running |
Right,
|
I built 6.1.54_1, and installed it on one of my 1Bs. While dkms itself didn't fail, the driver compilation did. I think it's unrelated, as it was trying to compile rtl8192cu from https://github.com/pvaret/rtl8192cu-fixes. That likely doesn't build for v6.1 anymore. EDIT: I have upgraded my "Raspberry Pi Model B Rev 2"s. Some have dkms modules, others not. They all seem to work as expected. |
cc12437
to
e2969f9
Compare
e2969f9
to
10094c4
Compare
|
|
i'm showing my own testing, not in total |
Ah. Sorry, mate. |
10094c4
to
6a2bd7d
Compare
On a clean install, dkms fails with the missing "bc" command (and package). Maybe we should add this as a dependency somewhere? Most probably to the "rpi-kernel-headers" package, as a successful And some other observation: Beside these findings, 400 and 02W (both musl) are working fine. Also building dkms modules works, e.g. with package "rtl8821cu-dkms". However, building "zfs" made the 02W unresponsive at some stage of the process. Maybe it's just too big for the machine to get it compiled with the small amount of RAM it has. Adding swap also did not fix it. Only other option I can think of would be to buid it with |
probably in the deps of dkms, not the headers. will address the dkms stuff separately (#46332) |
continuation of #43600, made a new PR to clean things up
builds for testing: https://devspace.voidlinux.org/abby/updates/rpi/
Testing the changes
Still getting the DKMS/headers issue:
When building
fixdep
andmodpost
in/etc/kernel.d/post-install/10-dkms
, it gets stuck in an infinite makefile loop:void-packages/srcpkgs/dkms/files/kernel.d/dkms.postinst
Lines 22 to 24 in 5b18878
However,
^C
ing out of that and re-running it succeeds, becausefixdep
andmodpost
were build before the infinite loop:And dkms works after that:
So the issue left to figure out is: why does it infinite loop?